slackware-10.0/extra/ham/install-packages failed: No space left on device (28) - " /> slackware-10.0/extra/ham/install-packages failed: No space left on device (28) rsync: [generator] link /slackware/slackware-10.2/slackware/l/install-packages" => slackware-10.0/extra/ham/install-packages failed: No space left on device (28) Just a reminder that rsync may report this error "No space left on device (28)&quo" /> slackware-10.0/extra/ham/install-packages failed: No space left on device (28) - " /> slackware-10.0/extra/ham/install-packages failed: No space left on device (28) rsync: [generator] link /slackware/slackware-10.2/slackware/l/install-packages" => slackware-10.0/extra/ham/install-packages failed: No space left on device (28) Just a reminder that rsync may report this error "No space left on device (28)&quo rsync, generator, slackware, install, packages, ham, quot, reminder, array, partition, df, inodes, various, fuse, distributed, filesystems, gluster, creating, symlinks, disable, hardlinks, links," />
rsync: [generator] link /slackware/slackware-10.2/slackware/l/install-packages" => slackware-10.0/extra/ham/install-packages failed: No space left on device (28)
Just a reminder that rsync may report this error "No space left on device (28)" even when it's true, meaning your array/partition has lots of space left and assuming df -i shows lots of inodes.
This can often happen on various file/fuse based distributed filesystems like gluster, especially when creating symlinks. You may have to disable symlinks and use hardlinks, or no links at all to solve this issue.
rsync, generator, slackware, install, packages, ham, quot, reminder, array, partition, df, inodes, various, fuse, distributed, filesystems, gluster, creating, symlinks, disable, hardlinks, links,